Repository navigation
docs: production state after 2026-09-30, and an exact approval rule for agents - #89
Merged
Merged
Conversation
…or agents - agents/integrate: every action needs a signed approval, reads included; the approval signal and resource for each connector action; the example request is refused until a person approves, and the page says so. - llms-full.txt now includes human approval, connect an agent, the connector development guide, writing a policy, the policy lifecycle, managing approvers and approval notifications. - customer-refund 1.2.0 and the 13 G-80 versions are approved and in effect: removed every "until it is approved" statement from the site, CLAIMS 2.47, G-80, CURRENT-STATE, REMAINING-WORK and PAYTM_CONNECTOR. - PowerShell proposal commands read policy.json as UTF-8. Get-Content -Raw in Windows PowerShell 5.1 changed an em dash, and CI refused the merge. - Credentials guide: approvers through maker checker, the correct code file, rotating the refund agent service, the 2026-09-30 rotation, and troubleshooting rows for the problems met that day. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Docs only. Brings the docs site and the repo records in line with production after 2026-09-30, and makes the agent integration page exact about approvals.
agents/integrate: it said an action's approval signals could be "none". Since G-80 that is false. The page now says every action needs a signed approval, reads included, and gives the approval signal, the resource it names and the other signals for every connector action (taken from the policy files in effect). The example request is marked as refused until a person approves.llms-full.txt, the single file crawling agents read, now includes Human approval, Connect an agent, the connector development guide, Write your first policy, Policy lifecycle, Manage approvers and Approval notifications.customer-refund1.2.0 (approved 2026-09-28) and the 13 G-80 versions (approved and deployed 2026-09-30) are in effect. Updated the site (human approval, end to end Paytm flow, changelog),CLAIMS.md2.47, G-80,CURRENT-STATE.md,REMAINING-WORK.mdandPAYTM_CONNECTOR.md.policy.jsonas UTF-8.Get-Content -Rawin Windows PowerShell 5.1 changed an em dash inconnector-capability1.1.0, so the approved hash differed from the file and CI refused PR No agent action without a signed human approval, reads included #87 until the exact content was approved.codeApprovalIssuers.ts), rotating the refund agent service's three values together, the 2026-09-30 rotation record, and troubleshooting rows for each problem met that day.Found, not fixed here
No endpoint tells an agent which signals a policy reads or which one needs an approval:
GET /policies/in-effectreturns only the name and version. The page now lists them for the connector actions; for other actions the agent must ask the operator. ReturningapprovalSignalsand the facts from that endpoint would remove the guess.Verified
Pre commit check passed: 2520 tests, docs architecture tests (links, llms files up to date, environment variables documented), lint, format, build.
🤖 Generated with Claude Code